Hi Tapio,
I assume you tried this with Stop
When Low checked or unchecked?
One remote possibility is
that noise is causing the signal to be both high and low (with a small duty
cycle so it may not be seen on the Digital I/O Screen).
Try running these two test routines to check for that and report
the results (test in the inactive state):
#include "KMotionDef.h"
// Simple check for Glitch on Input Pin
main()
{
while
(!ReadBit(1106)) ; // tight loop while input is low
printf("Input was high!!\n");
}
#include
"KMotionDef.h"
// Simple check for Glitch on Input
Pin
main()
{
while (ReadBit(46)) ; // tight loop while
input is low
printf("Input was low!!\n");
}
Regards
TK
| Group: DynoMotion |
Message: 11800 |
From: Tom Kerekes |
Date: 6/27/2015 |
| Subject: Re: Limit switch options?-SOLVED |
Hi Tapio,
Any Init file that runs at power up would indeed change parameters. But if it only changes them once and if you download new parameters from KMotion Screens (ie "Move") those should set new values. So I'm not sure why you see this effect unless your Init.c program is continuously executing in a loop or something. What is the program you are flashing in KFLOP? We don't recommend you have Launch on Power up programs as it can be confusing what was flashed in each board. It is usually better to leave KFLOP in a completely default state and just Initialize it from the PC with an Initialize Button.
Regards TK
| Group: DynoMotion |
Message: 11807 |
From: Tapio Larikka |
Date: 6/27/2015 |
| Subject: Re: Limit switch options?-SOLVED |
Hi Tom,
It ends up the cause was me not seeing the obvious,
once again.
I have virtual bit stated based limit options in
for;; loop at the end of my init.c file. I have these so that hitting the limit
will trip mach reset but to allow jogging off the limit once limits are
deactivated.
Thank you once again,
Tapio
----- Original Message -----
Sent: Saturday, June 27, 2015 9:05
PM
Subject: Re: [DynoMotion] Limit switch
options?-SOLVED
Hi Tapio,
Any Init file that runs at power up
would indeed change parameters. But if it only changes them once and if
you download new parameters from KMotion Screens (ie "Move") those should set
new values. So I'm not sure why you see this effect unless your Init.c
program is continuously executing in a loop or something. What is the
program you are flashing in KFLOP? We don't recommend you have Launch on
Power up programs as it can be confusing what was flashed in each board.
It is usually better to leave KFLOP in a completely default state and just
Initialize it from the PC with an Initialize Button.
Regards
TK
| | | |
